Bulk Delete

Free Bulk Delete

Keep Your Database Size Under Control

The premium features of Bulk Delete allow you to keep your database size under control by creating Delete Packages that can be scheduled to run via the Job Queue. Use advanced filtering and timeout options to keep log tables or historical transactions from growing out of control.

We’ve had a complete rethink of how the Bulk Delete processing should work and have come up with a new system which we are calling Delete Packages. Here’s an overview of the changes.

• Delete Packages allow you to define a set of tables that will be processed in a single package.
• Unlike Bulk Delete Requests which could not be edited after the first run, Delete Packages can be changed at any time.
• Tables within a package (called Delete Package Lines) can be reordered using Move Up and Move Down actions to change the execution order.
• A Delete Action for each line replaces the Store After Delete OK option (which included Record Identifier Only and Nothing as choices) which allows delete actions of Delete and Log, Delete Only, and Truncate. The truncate option does not run the standard delete triggers and is therefore only available in a Sandbox environment.
• A single Job Queue Entry codeunit will process all Delete Packages where the Job Queue Filter is set to Available for Processing. The Parameter String on the Job Queue Entry can be used as a filter for Delete Packages to be processed allowing a single Job Queue Entry to process all available packages or only those that match the filter.
• An option to add the delete history (the Delete Package Run details) to a package so that it will keep the log data under control.
• The progress dialog when deleting as a foreground task has been removed and has resulted in a noticeable performance increase.
• The counting of records now happens as a page background task meaning the page will render even if there are many millions of records that match the filter. Previously extremely large tables could have a significant delay when waiting for the record count to complete.
• Delete Package definitions can now be exported and imported which is a useful way to preserve “data clean-up” packages that get lost when a Sandbox is overwritten with a copy of Production.

Retention policies provide a great way of controlling your database size, but what if there are no retention policies in place for the tables that are growing out of control? Bulk delete allows you to create delete packages for any table and will use the standard delete validation rules for that table. When packages are run a Sandbox environment, the Truncate option can be used for ultra-fast clean-up. The truncate option is not available for all tables and does not execute validation logic which is why it is only available in a sandbox and not production.

Bulk Delete is perfect for day-to-day admin tasks, cleanup after import errors, or tidying up large record sets—this app gives you control, speed, and peace of mind. No development skills required.

To learn more, check out the Usage Scenarios topic in the online help.